![]() |
![]() |
![]() |
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
![]() |
![]() |
To access the contents, click the chapter and section titles.
Wireless Networking Handbook
Performing Acceptance TestingAfter the project team fully tests the system, its time for the customer to perform acceptance testing, which involves actual users running tests to determine whether the implementation is acceptable. These tests should focus on verifying whether the system functions as specified in the requirements. This does not require the same level of detail as system tests do. Acceptance testing is done at a much higher level to ensure users can run the appropriate applications while performing their jobs. For example, Mary will be using a wireless terminal tied to a central database to access inventory records as she stocks the shelves. Acceptance testing will determine whether she can actually enter and retrieve data from the database while handling the stock. Deploying the network/system to the entire population until a cross section of users performs the acceptance tests is not best. Most people refer to this as a system pilot. Acceptance testing as a pilot of the implementation is advisable if any of the following conditions are true:
In these cases, great risks in loosing productivity and valuable information exist if defects in the system occur. For instance, if you deploy a wireless inventory system at six warehouses and find that other existing devices interfere, then all warehouses stand to lose some productivity until the problem can be resolved. A pilot system at one of the warehouses would have identified the problem, and you could have fixed it before deploying the system to the remaining sites. The drawback of pilot testing, though, is that it delays the deployment of the system to the users not participating in the pilot. This could make it impossible to meet schedule deadlines. However, if the conditions above exist, running a pilot test will be worth the wait. Finalizing the ProjectAfter the user organization accepts the system, the project might seem to be over. Right? Actually, no. There are still some tasks left, including the following:
Updating DocumentationDuring the installation and testing phase, the team may have made changes to the design or layout of the network as a result of corrective actions to failed tests. Therefore, the team might need to update documentation, such as design specifications. In some extreme cases, requirements might need updating if the installed system cant support desired requirements as expected. Most companies refer to these updated documents as installed or red-lined drawings. These drawings provide an accurate set of documentation for support staff to use when troubleshooting or modifying the system. Training UsersAs described in Chapter 9, Preparing for the Support of a Wireless Network, training users and, if necessary, the support staff, is extremely important. Training strengthens the interface between the system and the users. If possible, offer the training before or during the system installation. Training prepares specific users for performing the acceptance testing and ensures all users are ready to start using the system when its operational. You can implement a small implementation of the system in a classroom and teach people how to use the system before it is actually deployed to the rest of the company. Transferring the Network to Operational SupportWhile implementing the network, the project team provides support for the network, such as the creation of user accounts, and troubleshooting and repair actions. In fact, during the requirements phase and acceptance testing, potential users generally assume that members of the project team will always be providing support. In some cases, this might be true. But, regardless of whether the team will be providing operational support, be sure to clearly transfer support of the operational network from the project team to applicable people and organizations. This transfer clearly marks the end of the project and ensures users having problems with the system will call upon the right people for assistance. Be certain as part of the transfer that the operational support staff have copies of network documentation, such as designs and support plans. Figure 10.11 illustrates the concept of transferring the network to operational support.
This transfer should mark the completion of a successful wireless network implementation. Soon, the numerous benefits of wireless networking will be apparent and your efforts will be justified. Evaluating the Outcome of the Project
|
![]() |
Products | Contact Us | About Us | Privacy | Ad Info | Home
Use of this site is subject to certain Terms & Conditions, Copyright © 1996-2000 EarthWeb Inc. All rights reserved. Reproduction whole or in part in any form or medium without express written permission of EarthWeb is prohibited. Read EarthWeb's privacy statement. |